Vitalik's Vision: The "Enshrined ZK-EVM" Explained

Table of Contents

The landscape of Layer-2 solutions for Ethereum has witnessed the rise of protocols like optimistic rollups and ZK rollups, each relying on Ethereum Virtual Machine (EVM) verification. However, the trust placed in a substantial codebase leaves these protocols vulnerable to potential hacks, prompting the need for a more secure and efficient approach. This article dives into the concept of an "enshrined ZK-EVM" within the Ethereum ecosystem, exploring its potential features, benefits, and the challenges it may pose.

I. Enshrining ZK-EVM in Ethereum

The Ethereum ecosystem, with its ever-growing complexity and scalability challenges, has spurred innovation in Layer-2 solutions. Among these solutions, optimistic rollups and ZK rollups have gained prominence, offering scalability by moving computational work off the Ethereum mainnet. However, a critical dependency on Ethereum Virtual Machine (EVM) verification introduces potential vulnerabilities, necessitating a deeper exploration of the concept of an "enshrined ZK-EVM."

Leveraging Ethereum's Governance

At the core of this concept lies the utilization of Ethereum's robust governance. Existing protocols often replicate the EVM verification functionality independently, leading to the duplication of efforts and potential security risks. The proposal suggests a paradigm shift—instead of creating separate verification mechanisms, why not integrate a native ZK-EVM into the Ethereum protocol itself?

By doing so, the Ethereum network could unify the process of verifying Layer-1 Ethereum blocks and ZK-EVMs. This alignment ensures that the Ethereum governance, already responsible for making upgrades and fixing bugs in the L1 EVM, oversees the ZK-EVM as well. This not only streamlines governance processes but also reduces the risk associated with maintaining distinct codebases for similar functionalities.

Compatibility with Multi-Client Philosophy

A crucial consideration in enshrining the ZK-EVM within Ethereum is maintaining compatibility with Ethereum's multi-client philosophy. Rather than endorsing a single proving system, the proposal advocates for a more versatile approach. The idea is to allow different clients to adopt various proving systems, fostering a diverse and adaptable ecosystem.

This compatibility extends beyond the implementation of the ZK-EVM itself. The proposed system should ensure data availability, guaranteeing that underlying data is accessible for different proving systems to re-prove executions. In this way, clients relying on varied proving systems can independently verify newly generated proofs.

By avoiding the enshrinement of a single proving system, the Ethereum network could pave the way for a decentralized ecosystem where users choose their preferred client. The influence of proving systems would be determined by user preferences and not dictated by a centralized governance process.

II. Key Properties and Implementation

As we delve into the design and implementation aspects of an enshrined ZK-EVM within Ethereum, several key properties and considerations come to the forefront, shaping the vision for this innovative proposal.

Basic Functionality and Auditability

At its core, the enshrined ZK-EVM must uphold the basic functionality of verifying Ethereum blocks. Whether through the introduction of opcodes, precompiles, or another mechanism, the protocol feature must seamlessly integrate with the Ethereum ecosystem. The proposed design entails accepting essential inputs such as pre-state root, block, and post-state root, ensuring a robust verification process.

An additional layer of significance in the design is auditability. In the event of any discrepancies or unforeseen issues, it is crucial for users and developers to inspect the underlying data. This requirement not only enhances transparency but also establishes a safeguard, allowing for thorough examination and analysis in case of unexpected outcomes.

source: note.ethereum.org - Vitalik Buterin

Speed and Challenges in Achieving It

One of the pivotal considerations in implementing the enshrined ZK-EVM is the speed of verification. While it's conceivable to design an asynchronous ZK-EVM feature, returning answers with a delay, the preference is for a system that reliably generates proofs within a few seconds. This approach ensures that each block's execution remains self-contained, contributing to the overall efficiency of the Ethereum network.

While the theoretical potential for massive parallelization exists, allowing the use of GPUs, recursive SNARKs, and hardware acceleration through FPGAs and ASICs, achieving rapid proof generation presents a significant engineering challenge. The community acknowledges that transitioning from the current prolonged proof generation times to a near-instantaneous process requires careful engineering and technological advancements.

In summary, the enshrined ZK-EVM aims to strike a balance between basic functionality, auditability, and the need for speedy verification. As the community navigates the challenges associated with achieving this vision, the emphasis remains on creating a system that seamlessly integrates into Ethereum's ecosystem while pushing the boundaries of efficiency.

III. Philosophical Considerations and Extensions

The philosophical considerations surrounding the enshrined ZK-EVM concept delve into the pivotal choice between an "open" and "closed" multi-client system, as well as the support for "almost-EVMs" and the exploration of stateful provers.

Open vs. Closed Systems

The debate between an "open" and "closed" multi-client system encapsulates fundamental decisions about the governance and adaptability of the proposed ZK-EVM. An open system, though more complex, aligns with the principles of decentralization and user autonomy that have been integral to Ethereum's ethos. By allowing proofs to reside outside the block and be verified independently by clients, this approach empowers users to choose their preferred proving system.

Conversely, a closed system simplifies the design by fixing the number of approved proof systems. However, it introduces governance complexities, requiring a structured process for incorporating new proof systems. The trade-off between simplicity and adaptability leans toward an open multi-client system, where the dynamism of user choice and decentralization outweigh the challenges posed by increased complexity.

Supporting Almost-EVMs and Stateful Provers

The enshrined ZK-EVM concept doesn't merely aim for replication but embraces innovation. Supporting "almost-EVMs" signifies a commitment to allowing Layer-2 solutions to innovate on the execution layer. The proposal suggests a flexible design that enables Layer-2 projects to extend the EVM with new precompiles, opcodes, and even parallel EVMs with synchronous cross-communication. This feature enhances the value proposition for Layer-2 projects, encouraging creativity and differentiation within the Ethereum ecosystem.

The exploration of stateful provers addresses concerns related to data efficiency. While the initial design is stateless, introducing the option for a stateful EVM opens avenues for optimization. By considering previously used or generated blobs as a dictionary, the system aims to compress data efficiently. This not only addresses storage concerns but also reflects a forward-looking approach to resource optimization within the Ethereum network.

IV. Future Roles

As the Ethereum ecosystem contemplates the introduction of an enshrined ZK-EVM, the implications for the roles of Layer 2 projects are poised to evolve. The future landscape sees a nuanced distribution of responsibilities and functions, marking a significant paradigm shift in how Layer 2 solutions operate within the Ethereum network.

Evolving Responsibilities of Layer 2 Projects

Layer 2 projects, historically at the forefront of implementing EVM verification independently, would witness a notable transformation in their roles. While the EVM verification functionality may transition to the protocol level, Layer 2 projects retain crucial responsibilities that contribute to the overall health and efficiency of the Ethereum ecosystem.

Fast Pre-Confirmations:

Layer 2 projects have excelled in providing users with fast pre-confirmations, leveraging their own security models to reduce latency significantly. This service, backed by the Layer 2's security infrastructure, remains a pivotal responsibility. As single-slot finality potentially slows down Layer 1 slots, Layer 2 projects continue to offer users quick pre-confirmations, ensuring a seamless and rapid user experience.

MEV Mitigation Strategies:

Mitigating Miner Extractable Value (MEV) remains a challenge at the forefront of blockchain scalability. Layer 2 projects are well-positioned to continue developing and implementing MEV mitigation strategies. These may include encrypted mempools, reputation-based sequencer selection, and other features that Layer 1 might not be willing to implement. Layer 2 projects continue to be the front line of defense against MEV-related issues.

Extensions to the EVM:

Layer 2 projects have been instrumental in introducing extensions to the EVM, providing added functionalities and features. This role remains crucial as these projects can innovate and introduce valuable enhancements. Whether it involves supporting "almost-EVMs," introducing new precompiles, or radically different approaches, Layer 2 projects continue to be hubs of innovation within the Ethereum ecosystem.

source: note.ethereum.org - Vitalik Buterin

User and Developer-Facing Conveniences:

Layer 2 teams have played a significant role in attracting users and projects to their ecosystems. This involves creating a user-friendly environment and offering conveniences that enhance the overall experience. Even with the introduction of an enshrined ZK-EVM, Layer 2 projects would remain instrumental in user and developer onboarding, making Ethereum more accessible to a broader audience.

Conclusion on Enshrined ZK-EVM Concept

In conclusion, the introduction of an enshrined ZK-EVM in Ethereum represents a significant step towards optimizing and securing Layer 2 solutions. By integrating ZK-EVM verification into the Ethereum protocol, the network aims to streamline governance processes and enhance security. However, this evolution doesn't render Layer 2 projects obsolete; instead, it redistributes their roles.

The Ethereum community envisions a future where Layer 2 projects continue to thrive, focusing on areas where their expertise and agility shine. While the protocol handles fundamental aspects of ZK-EVM verification, Layer 2 projects remain indispensable in providing swift pre-confirmations, implementing MEV mitigation, extending the EVM, and offering user-centric conveniences.

The enshrined ZK-EVM concept, therefore, represents a collaborative evolution, where both the protocol and Layer 2 projects contribute synergistically to a more robust, efficient, and user-friendly Ethereum ecosystem. As the community navigates this dynamic shift, the goal remains clear: to foster innovation, improve scalability, and provide an optimal blockchain experience for users and developers alike.

About Orochi Network

Orochi Network is a cutting-edge zkOS (An operating system based on zero-knowledge proof) designed to tackle the challenges of computation limitation, data correctness, and data availability in the Web3 industry. With the well-rounded solutions for Web3 Applications, Orochi Network omits the current performance-related barriers and makes ways for more comprehensive dApps hence, becoming the backbone of Web3's infrastructure landscape.